Skip to content

Remove Gradle .module files from Maven package validation#1370

Open
ramsessanchez wants to merge 1 commit into
mainfrom
ramsessanchez/fix-validate-package-module-file
Open

Remove Gradle .module files from Maven package validation#1370
ramsessanchez wants to merge 1 commit into
mainfrom
ramsessanchez/fix-validate-package-module-file

Conversation

@ramsessanchez

@ramsessanchez ramsessanchez commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes a package-validation failure in the CI build:

Expected file microsoft-graph-beta-6.60.1.module not found in package.
##[error]PowerShell exited with code '1'.

Root cause

scripts/validatePackageContents.ps1 expected .module and .module.asc files. These are Gradle Module Metadata artifacts. The pipeline builds and publishes with Maven (./mvnw), which does not generate .module files. This mismatch was introduced during the Gradle to Maven ESRP migration.

Change

Removed .module and .module.asc from the expected-files list. The remaining validated artifacts (.jar, -sources.jar, -javadoc.jar, .pom and their .asc signatures) are all produced by the Maven build.

Microsoft Reviewers: Open in CodeFlow

validatePackageContents.ps1 expected .module and .module.asc files,
which are Gradle Module Metadata artifacts. The pipeline publishes with
Maven (./mvnw), which does not generate .module files, causing the
validation step to fail. Remove the two Gradle-only entries from the
expected files list.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: ca8303b0-dcb7-467f-9d6b-7f68da829576
@ramsessanchez ramsessanchez requested a review from a team as a code owner July 14, 2026 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants